Systems and methods for displaying trustworthiness classifications for files as visually overlaid icons

ABSTRACT

A computer-implemented method for displaying trustworthiness classifications for files as visually overlaid icons may include (1) identifying a file, (2) identifying a file icon that graphically represents the file within a file manager interface on a computing device, (3) obtaining a trustworthiness classification assigned to the file that identifies the trustworthiness of the file, and then (4) visually overlaying the file icon with a trustworthiness icon that graphically represents the trustworthiness classification assigned to the file. Various other systems, methods, and computer-readable media are also disclosed.

BACKGROUND

Security software may attempt to determine the trustworthiness of a fileusing various heuristics and/or based on various community-suppliedinformation about the file. For example, security software may attemptto determine whether a file is malicious by determining whether the filematches a unique digital signature or fingerprint associated with aknown-malicious file. Additionally or alternatively, the securitysoftware may attempt to assess the trustworthiness of the file byobtaining a reputation score for the file from a reputation service. Inthis example, the reputation service may assign the reputation score tothe file by collecting, aggregating, and analyzing data from potentiallymillions of user devices within a community (such as the user base of asecurity-software vendor) that identify, among other details, the file'sorigin, age, and prevalence within the community (such as whether thefile is predominantly found on at-risk or “unhealthy” machines withinthe community).

Unfortunately, while a user may (in some cases) see the results of sucha trustworthiness evaluation immediately upon its completion, the usermay fail to recall the results of the trustworthiness evaluation at afuture point in time (e.g., when viewing files within a file managerinterface). Thus, the user may be unable to identify the trustworthinessof a file displayed within a file manager interface without requesting aseparate evaluation of the file's trustworthiness. Consequently, if theuser fails to request a separate trustworthiness evaluation prior toopening or executing a file, the user may unknowingly open or execute afile that is less trustworthy than another file that performs asubstantially similar function. For example, the user may unknowinglyexecute a calculator application that is less trustworthy than anothercalculator application stored in the same directory.

As such, the instant disclosure identifies a need for systems andmethods for enabling users to quickly and easily identify (and/orcompare) the trustworthiness of files without having to request aseparate evaluation of the files' trustworthiness.

SUMMARY

As will be described in greater detail below, the instant disclosuregenerally relates to systems and methods for displaying trustworthinessclassifications for files as visually overlaid icons. In one example, ashell extension (such as a security plug-in) for a file managerinterface may accomplish such a goal by (1) identifying a file icon thatgraphically represents a file within a file manager interface (such asMICROSOFT WINDOWS EXPLORER) on a computing device, (2) obtaining atrustworthiness classification assigned to the file that identifies thetrustworthiness or reputation of the file, and then (3) visuallyoverlaying the file icon with a trustworthiness icon that graphicallyrepresents the trustworthiness classification assigned to the file. Inthis example, the trustworthiness icon may enable a user of thecomputing device to quickly and easily visually identify the file'strustworthiness or reputation without having to request a separateevaluation of the file.

As will be explained in greater detail below, by visually overlayingfile icons with corresponding trustworthiness icons, the various systemsand methods described herein may enable users to visually identify(and/or compare) the trustworthiness or reputations of files within afile manager interface without having to request separatetrustworthiness evaluations of the same.

Features from any of the above-mentioned embodiments may be used incombination with one another in accordance with the general principlesdescribed herein. These and other embodiments, features, and advantageswill be more fully understood upon reading the following detaileddescription in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodimentsand are a part of the specification. Together with the followingdescription, these drawings demonstrate and explain various principlesof the instant disclosure.

FIG. 1 is a block diagram of an exemplary system for displayingtrustworthiness classifications for files as visually overlaid icons.

FIG. 2 is a flow diagram of an exemplary method for displayingtrustworthiness classifications for files as visually overlaid icons.

FIG. 3 is an illustration of an exemplary overlay process.

FIG. 4 is an illustration of an exemplary file manager interfaceincluding trustworthiness classifications for files displayed asvisually overlaid icons.

FIG. 5 is a block diagram of an exemplary computing system capable ofimplementing one or more of the embodiments described and/or illustratedherein.

FIG. 6 is a block diagram of an exemplary computing network capable ofimplementing one or more of the embodiments described and/or illustratedherein.

Throughout the drawings, identical reference characters and descriptionsindicate similar, but not necessarily identical, elements. While theexemplary embodiments described herein are susceptible to variousmodifications and alternative forms, specific embodiments have beenshown by way of example in the drawings and will be described in detailherein. However, the exemplary embodiments described herein are notintended to be limited to the particular forms disclosed. Rather, theinstant disclosure covers all modifications, equivalents, andalternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

As will be described in greater detail below, the instant disclosuregenerally relates to systems and methods for displaying trustworthinessclassifications for files as visually overlaid icons. The following willprovide, with reference to FIG. 1, detailed descriptions of exemplarysystems for displaying trustworthiness classifications for files asvisually overlaid icons. Detailed descriptions of correspondingcomputer-implemented methods will also be provided in connection withFIGS. 2-4. In addition, detailed descriptions of an exemplary computingsystem and network architecture capable of implementing one or more ofthe embodiments described herein will be provided in connection withFIGS. 5 and 6, respectively.

FIG. 1 is a block diagram of an exemplary system 100 for displayingtrustworthiness classifications for files as visually overlaid icons. Asillustrated in this figure, exemplary system 100 may include one or moremodules 102 for performing one or more tasks. For example, and as willbe explained in greater detail below, exemplary system 100 may includean identification module 104 programmed to identify a file icon thatgraphically represents a file within a file manager interface. Exemplarysystem 100 may also include a classification module 106 programmed toobtain a trustworthiness classification assigned to the file thatidentifies the trustworthiness or reputation of the file.

In addition, and as will be described in greater detail below, exemplarysystem 100 may include an overlay module 108 programmed to visuallyoverlay the file icon with a trustworthiness icon that graphicallyrepresents the trustworthiness classification assigned to the file.Although illustrated as separate elements, one or more of modules 102 inFIG. 1 may represent portions of a single module or application (such asa shell extension, a security plug-in, or a file manager interface).

In certain embodiments, one or more of modules 102 in FIG. 1 mayrepresent one or more software applications or programs that, whenexecuted by a computing device, may cause the computing device toperform one or more tasks. For example, as will be described in greaterdetail below, one or more of modules 102 may represent software modulesstored and configured to run on one or more computing devices, such ascomputing system 510 in FIG. 5 and/or portions of exemplary networkarchitecture 600 in FIG. 6. One or more of modules 102 in FIG. 1 mayalso represent all or portions of one or more special-purpose computersconfigured to perform one or more tasks.

As illustrated in FIG. 1, exemplary system 100 may also include one ormore databases, such as classification database 120. Classificationdatabase 120 may represent portions of a single database or computingdevice or a plurality of databases or computing devices. In oneembodiment, and as will be explained in greater detail below,classification database 120 may store trustworthiness classifications122 assigned to files.

Classification database 120 in FIG. 1 may represent a portion of one ormore computing devices. For example, classification database 120 mayrepresent a portion of computing system 510 in FIG. 5 and/or portions ofexemplary network architecture 600 in FIG. 6. Alternatively,classification database 120 in FIG. 1 may represent one or morephysically separate devices capable of being accessed by a computingdevice, such as computing system 510 in FIG. 5 and/or portions ofexemplary network architecture 600 in FIG. 6.

Exemplary system 100 in FIG. 1 may be deployed in a variety of ways. Inone example, all or a portion of exemplary system 100 may representportions of computing system 510 in FIG. 5. For example, and as will bedescribed in greater detail below, in some examples modules 102 mayprogram computing system 510 to display trustworthiness classificationsassigned to files as visually overlaid icons by (1) identifying a fileicon that graphically represents a file within a file manager interface(such as file manager interface 400 in FIG. 4) on computing system 510,(2) obtaining a trustworthiness classification assigned to the file(from, e.g., classification database 120 in FIG. 1) that identifies thetrustworthiness or reputation of the file, and then (3) visuallyoverlaying the file icon with a trustworthiness icon that graphicallyrepresents the trustworthiness classification assigned to the file.

FIG. 2 is a flow diagram of an exemplary computer-implemented method 200for displaying trustworthiness classifications for files as visuallyoverlaid icons. The steps shown in FIG. 2 may be performed by anysuitable computer-executable code and/or computing system. In someembodiments, the steps shown in FIG. 3 may be performed by one or moreof the components of system 100 in FIG. 1, computing system 510 in FIG.5, and/or exemplary network architecture 600 in FIG. 6.

As illustrated in FIG. 2, at step 202 the various systems describedherein may identify a file. For example, identification module 104 may,as part of computing system 510 in FIG. 5, identify a file encounteredby computing system 510.

The systems described herein may perform step 202 in a variety of ways.In one example, identification module 104 may identify a file uponobserving or detecting creation of the file. For example, identificationmodule 104 may identify an executable file that is created and storedwithin a directory on computing system 510 as part of an installationprocess. In another example, identification module 104 may identify afile within a directory as an application (or operating system) analyzesthe contents of the directory prior to causing the contents of thedirectory to be displayed within a file manager interface (such as filemanager interface 400 in FIG. 4). Identification module 104 may alsoidentify files upon encountering the same on local and/or remote storagedevices (e.g., files stored on removable storage devices and/or remoteservers). The file identified in step 202 may be any type of file,including an executable file or a dynamic-link library file.

Returning to FIG. 2, at step 204 the various systems described hereinmay identify a file icon used to graphically represent the file within afile manager interface on a computing device. For example,identification module 104 may, as part of computing system 510 in FIG.5, identify a file icon 302 in FIGS. 3 and 4 that is used to graphicallyrepresent the file “Wincalc.exe” within file manager interface 400 inFIG. 4.

The term “file icon,” as used herein, generally refers to any type orform of pictogram used to visually or graphically represent an object(such as a file, folder, application, device, etc.) within a graphicaluser interface of a computing system. As will be explained in greaterdetail below, file icons may graphically represent objects using any ofa variety of shapes, text, sizes, colors, and/or animations.

In addition, the term “file manager interface,” as used herein,generally refers to any type or form of user interface for enablingusers to view and/or manipulate files within a file system. File managerinterfaces may display various images that graphically represent one ormore files, relative or absolute paths, computing resources, and/or anyother type of suitable information. In some examples, file managerinterfaces may be presented to a user of a computing system in responseto one or more user actions (e.g., upon selecting an application iconthat represents the file manager interface). Examples of file managerinterfaces include, without limitation, orthodox file managers (such asMICROSOFT SE-EXPLORER or WINSCP), navigational file managers (such asMICROSOFT WINDOWS EXPLORER or MAC OS X FINDER), spatial file managers,3D file managers, web-based file managers, or any other suitable type offile manager or user interface.

The systems described herein may perform step 204 in a variety of ways.In one example, identification module 104 may identify a file iconassociated with a file upon creation of the same by an application oroperating system (e.g., during installation of the file or anapplication associated with the file). In other examples, identificationmodule 104 may identify a file icon associated with a file uponencountering the file (e.g., upon encountering a file on a removablestorage device and/or remote server).

Returning to FIG. 2, at step 206 the various systems described hereinmay obtain a trustworthiness classification assigned to the file thatidentifies the trustworthiness or reputation of the file. For example,classification module 106 may, as part of computing system 510 in FIG.5, obtain a trustworthiness classification 310 in FIG. 3 for theexecutable file “Wincalc.exe” from classification database 120 inFIG. 1. In this example, trustworthiness classification 310 may includeinformation that identifies a reputation of the executable file“Wincalc.exe” within a community, such as the user base of asecurity-software vendor.

The systems described herein may perform step 206 in a variety of ways.In one example, classification module 106 may obtain the trustworthinessclassification from a local database, such as classification database120 stored on computing system 510. In another example, classificationmodule 106 may obtain the trustworthiness classification from a remotereputation service.

The term “trustworthiness classification,” as used herein, generallyrefers to any type or form of information used to indicate or identifythe trustworthiness or reputation of an object (such as a file,application, device, computing resource, etc.) within a community (suchas the user base of a security-software vendor). As illustrated byexemplary trustworthiness classification 310 in FIG. 3, examples of thetypes of information that may be included within a trustworthinessclassification include the name of a file (in this example,“Wincalc.exe”), a hash of the file (in this example, “0xAD93C931”),and/or a numeric trustworthiness score that represents the file'strustworthiness or reputation within a community (in this example,“99%”). In this example, a high trustworthiness score may indicate thata file is generally trusted within the community, and a lowtrustworthiness score may indicate that a file is generally untrustedwithin the community.

As will be explained in greater detail below, trustworthinessclassifications may indicate that a particular file is trustworthy,untrustworthy, or that the file's trustworthiness is unknown. In variousexamples, trustworthiness classifications assigned to files may indicatethat the files are untrustworthy even though the files are notnecessarily malicious. For example, a reputation service may classify anon-malicious file as untrustworthy due to the file's poor performance(e.g., slow execution speed or high probability of failure), the file'spoor design, or any other characteristic relevant to the file'strustworthiness.

In some embodiments, reputation services (such as server 640 in FIG. 6)may generate a trustworthiness classification for a file based at leastin part on the file's location, origin, age, prevalence within acommunity, or any other characteristic relevant to classifying thetrustworthiness of the file. Reputation services may generatetrustworthiness classifications for files based at least in part oninformation that has been collected and aggregated from user deviceswithin a community. Examples of information gathered from user deviceswithin a community that may be used to generate trustworthinessclassifications include, without limitation, information that identifiesthe overall health of a user device (e.g., information that identifiesthe performance, stability, and/or state of security of the userdevice), information that identifies one or more files stored on orencountered by a user device, information that identifies the impact ofa file on the health of a user device (e.g., information that identifiesthe health of a user device both before and after a file is encounteredby the user device), or any other information relevant to classifyingthe trustworthiness of a file.

In some examples, by collecting, aggregating, and analyzing this datafrom potentially millions of user devices within a community (such asthe user base of a security-software vendor), a reputation service maybe able to gain a fairly accurate understanding as to thetrustworthiness of a file. In other examples, if little informationexists on a particular file within a community (e.g., if the file'sprevalence is low within the community), a reputation service may assigna trustworthiness classification to a file that indicates that thefile's trustworthiness is unknown.

Returning to FIG. 2, at step 208 the various systems described hereinmay visually overlay the file icon with a trustworthiness icon thatgraphically represents the trustworthiness classification assigned tothe file. For example, overlay module 108 may, as part of computingsystem 510 in FIG. 5, visually overlay file icon 302 in FIGS. 3 and 4with a trustworthiness icon 304 that graphically represents thetrustworthiness classification obtained in step 206. In this example,trustworthiness icon 304 may enable a user of computing system 510 toquickly and easily visually identify the file's trustworthiness (i.e.,without having to request a separate evaluation of the file'strustworthiness).

The term “trustworthiness icon,” as used herein, generally refers to anytype or form of pictogram used to visually or graphically represent thetrustworthiness of an object (such as a file, folder, application,device, computing resource, etc.) within a graphical user interface of acomputing system. As will be explained in greater detail below,trustworthiness icons may graphically represent the trustworthiness ofobjects using any of a variety of shapes, texts, sizes, colors, and/oranimations.

The systems described herein may perform step 208 in a variety of ways.In some examples, overlay module 108 may generate or identify atrustworthiness icon that graphically represents the trustworthinessclassification identified in step 206. In such examples, upon generatingor identifying the trustworthiness icon, overlay module 108 may overlay(or cause the file manager interface to overlay) the file iconidentified in step 204 with the trustworthiness icon.

For example, upon determining that trustworthiness classification 310 inFIG. 3 obtained for the executable file “Wincalc.exe” indicates that thefile is trustworthy, overlay module 108 may, as part of overlay process308 in FIG. 3, (1) generate or identify a trustworthiness icon 304 thatvisually suggests that executable file “Wincalc.exe” is trustworthy andthen (2) visually overlay file icon 302 with trustworthiness icon 304 toenable a user to visually identify that executable file “Wincalc.exe” istrustworthy without having to request a separate evaluation of thefile's trustworthiness.

In one example, if the trustworthiness classification obtained in step206 indicates that the file identified in step 202 is trustworthy,overlay module 108 may generate or identify a trustworthiness icon thatvisually suggests to a user that the file associated with thetrustworthiness icon is trustworthy. For example, upon determining thattrustworthiness classification 310 in FIG. 3 indicates that theexecutable file “Wincalc.exe” is trustworthy, overlay module 108 maygenerate and then overlay file icon 302 with a green-coloredtrustworthiness icon 304 that includes a check mark to visually conveythat the file “Wincalc.exe” is trustworthy.

In contrast, if the trustworthiness classification indicates that thefile identified in step 202 is untrustworthy, overlay module 108 maygenerate or identify a trustworthiness icon that visually suggests to auser that the file associated with the trustworthiness icon isuntrustworthy. For example, upon determining that the trustworthinessclassification associated with the executable file “Customcalc.exe”indicates that the file is untrustworthy, overlay module 108 maygenerate and then overlay file icon 410 in FIG. 4 with a red-coloredtrustworthiness icon 412 that includes an “X” to visually convey thatthe file “Customcalc.exe” is untrustworthy. In this example, theexecutable file “Customcalc.exe” may be a non-malicious file thatimplements a poorly designed calculator application when executed bycomputing system 510.

In another example, if the trustworthiness classification indicates thatthe trustworthiness of the file identified in step 202 is unknown,overlay module 108 may generate or identify a trustworthiness icon thatvisually suggests to a user that the trustworthiness of the fileassociated with the trustworthiness icon is unknown. For example,overlay module 108 may generate or identify a black-and-white coloredtrustworthiness icon that includes a question mark to visually conveythat the trustworthiness of a file is unknown.

In some embodiments, modules 102 may represent a portion of a shellextension within a file manager interface, such as file managerinterface 400 in FIG. 4. The term “shell extension,” as used herein,generally refers to any type of plug-in or software module configured toextend the functionality of a file manger interface beyond its defaultfunctionality. Such a shell extension may be provided as part of athird-party software package. For example, NORTON ANTIVIRUS may includeand provide a shell extension configured to extend the functionality ofMICROSOFT WINDOWS EXPLORER to overlay file icons with correspondingtrustworthiness icons. In this example, the shell extension may causeMICROSOFT WINDOWS EXPLORER to visually overlay a file icon with atrustworthiness icon.

As detailed above, the various systems and methods described herein mayenable users to visually compare the trustworthiness of files thatperform substantially similar functions without having to requestseparate trustworthiness evaluations of the same. For example, a usermay determine, by visually comparing trustworthiness icon 412 withtrustworthiness icon 304 in FIG. 4, that the executable file“Wincalc.exe” represents a safer (or at least more reputable or trusted)calculator application than the executable file “Customcalc.exe.” Thus,by visually overlaying file icons with corresponding trustworthinessicons, the various systems and methods described herein may enable usersto visually identify (and/or compare) the trustworthiness of fileswithin a file manager interface without having to request separatetrustworthiness evaluations.

FIG. 5 is a block diagram of an exemplary computing system 510 capableof implementing one or more of the embodiments described and/orillustrated herein. Computing system 510 broadly represents any singleor multi-processor computing device or system capable of executingcomputer-readable instructions. Examples of computing system 510include, without limitation, workstations, laptops, client-sideterminals, servers, distributed computing systems, handheld devices, orany other computing system or device. In its most basic configuration,computing system 510 may include at least one processor 514 and a systemmemory 516.

Processor 514 generally represents any type or form of processing unitcapable of processing data or interpreting and executing instructions.In certain embodiments, processor 514 may receive instructions from asoftware application or module. These instructions may cause processor514 to perform the functions of one or more of the exemplary embodimentsdescribed and/or illustrated herein. For example, processor 514 mayperform and/or be a means for performing, either alone or in combinationwith other elements, one or more of the identifying, obtaining, visuallyoverlaying, enabling, receiving, and providing steps described herein.Processor 514 may also perform and/or be a means for performing anyother steps, methods, or processes described and/or illustrated herein.

System memory 516 generally represents any type or form of volatile ornon-volatile storage device or medium capable of storing data and/orother computer-readable instructions. Examples of system memory 516include, without limitation, random access memory (RAM), read onlymemory (ROM), flash memory, or any other suitable memory device.Although not required, in certain embodiments computing system 510 mayinclude both a volatile memory unit (such as, for example, system memory516) and a non-volatile storage device (such as, for example, primarystorage device 532, as described in detail below). In one example, oneor more of modules 102 from FIG. 1 may be loaded into system memory 516.

In certain embodiments, exemplary computing system 510 may also includeone or more components or elements in addition to processor 514 andsystem memory 516. For example, as illustrated in FIG. 5, computingsystem 510 may include a memory controller 518, an Input/Output (I/O)controller 520, and a communication interface 522, each of which may beinterconnected via a communication infrastructure 512. Communicationinfrastructure 512 generally represents any type or form ofinfrastructure capable of facilitating communication between one or morecomponents of a computing device. Examples of communicationinfrastructure 512 include, without limitation, a communication bus(such as an ISA, PCI, PCIe, or similar bus) and a network.

Memory controller 518 generally represents any type or form of devicecapable of handling memory or data or controlling communication betweenone or more components of computing system 510. For example, in certainembodiments memory controller 518 may control communication betweenprocessor 514, system memory 516, and I/O controller 520 viacommunication infrastructure 512. In certain embodiments, memorycontroller 518 may perform and/or be a means for performing, eitheralone or in combination with other elements, one or more of the steps orfeatures described and/or illustrated herein, such as identifying,obtaining, visually overlaying, enabling, receiving, and providing.

I/O controller 520 generally represents any type or form of modulecapable of coordinating and/or controlling the input and outputfunctions of a computing device. For example, in certain embodiments I/Ocontroller 520 may control or facilitate transfer of data between one ormore elements of computing system 510, such as processor 514, systemmemory 516, communication interface 522, display adapter 526, inputinterface 530, and storage interface 534. I/O controller 520 may beused, for example, to perform and/or be a means for performing, eitheralone or in combination with other elements, one or more of theidentifying, obtaining, visually overlaying, enabling, receiving, andproviding steps described herein. I/O controller 520 may also be used toperform and/or be a means for performing other steps and features setforth in the instant disclosure.

Communication interface 522 broadly represents any type or form ofcommunication device or adapter capable of facilitating communicationbetween exemplary computing system 510 and one or more additionaldevices. For example, in certain embodiments communication interface 522may facilitate communication between computing system 510 and a privateor public network including additional computing systems. Examples ofcommunication interface 522 include, without limitation, a wired networkinterface (such as a network interface card), a wireless networkinterface (such as a wireless network interface card), a modem, and anyother suitable interface. In at least one embodiment, communicationinterface 522 may provide a direct connection to a remote server via adirect link to a network, such as the Internet. Communication interface522 may also indirectly provide such a connection through, for example,a local area network (such as an Ethernet network), a personal areanetwork, a telephone or cable network, a cellular telephone connection,a satellite data connection, or any other suitable connection.

In certain embodiments, communication interface 522 may also represent ahost adapter configured to facilitate communication between computingsystem 510 and one or more additional network or storage devices via anexternal bus or communications channel. Examples of host adaptersinclude, without limitation, SCSI host adapters, USB host adapters, IEEE1394 host adapters, SATA and eSATA host adapters, ATA and PATA hostadapters, Fibre Channel interface adapters, Ethernet adapters, or thelike. Communication interface 522 may also allow computing system 510 toengage in distributed or remote computing. For example, communicationinterface 522 may receive instructions from a remote device or sendinstructions to a remote device for execution. In certain embodiments,communication interface 522 may perform and/or be a means forperforming, either alone or in combination with other elements, one ormore of the identifying, obtaining, visually overlaying, enabling,receiving, and providing steps disclosed herein. Communication interface522 may also be used to perform and/or be a means for performing othersteps and features set forth in the instant disclosure.

As illustrated in FIG. 5, computing system 510 may also include at leastone display device 524 coupled to communication infrastructure 512 via adisplay adapter 526. Display device 524 generally represents any type orform of device capable of visually displaying information forwarded bydisplay adapter 526. Similarly, display adapter 526 generally representsany type or form of device configured to forward graphics, text, andother data from communication infrastructure 512 (or from a framebuffer, as known in the art) for display on display device 524.

As illustrated in FIG. 5, exemplary computing system 510 may alsoinclude at least one input device 528 coupled to communicationinfrastructure 512 via an input interface 530. Input device 528generally represents any type or form of input device capable ofproviding input, either computer or human generated, to exemplarycomputing system 510. Examples of input device 528 include, withoutlimitation, a keyboard, a pointing device, a speech recognition device,or any other input device. In at least one embodiment, input device 528may perform and/or be a means for performing, either alone or incombination with other elements, one or more of the identifying,obtaining, visually overlaying, enabling, receiving, and providing stepsdisclosed herein. Input device 528 may also be used to perform and/or bea means for performing other steps and features set forth in the instantdisclosure.

As illustrated in FIG. 5, exemplary computing system 510 may alsoinclude a primary storage device 532 and a backup storage device 533coupled to communication infrastructure 512 via a storage interface 534.Storage devices 532 and 533 generally represent any type or form ofstorage device or medium capable of storing data and/or othercomputer-readable instructions. For example, storage devices 532 and 533may be a magnetic disk drive (e.g., a so-called hard drive), a floppydisk drive, a magnetic tape drive, an optical disk drive, a flash drive,or the like. Storage interface 534 generally represents any type or formof interface or device for transferring data between storage devices 532and 533 and other components of computing system 510. In one example,classification database 120 from FIG. 1 may be stored in primary storagedevice 532.

In certain embodiments, storage devices 532 and 533 may be configured toread from and/or write to a removable storage unit configured to storecomputer software, data, or other computer-readable information.Examples of suitable removable storage units include, withoutlimitation, a floppy disk, a magnetic tape, an optical disk, a flashmemory device, or the like. Storage devices 532 and 533 may also includeother similar structures or devices for allowing computer software,data, or other computer-readable instructions to be loaded intocomputing system 510. For example, storage devices 532 and 533 may beconfigured to read and write software, data, or other computer-readableinformation. Storage devices 532 and 533 may also be a part of computingsystem 510 or may be a separate device accessed through other interfacesystems.

In certain embodiments, storage devices 532 and 533 may be used, forexample, to perform and/or be a means for performing, either alone or incombination with other elements, one or more of the identifying,obtaining, visually overlaying, enabling, receiving, and providing stepsdisclosed herein. Storage devices 532 and 533 may also be used toperform and/or be a means for performing other steps and features setforth in the instant disclosure.

Many other devices or subsystems may be connected to computing system510. Conversely, all of the components and devices illustrated in FIG. 5need not be present to practice the embodiments described and/orillustrated herein. The devices and subsystems referenced above may alsobe interconnected in different ways from that shown in FIG. 5. Computingsystem 510 may also employ any number of software, firmware, and/orhardware configurations. For example, one or more of the exemplaryembodiments disclosed herein may be encoded as a computer program (alsoreferred to as computer software, software applications,computer-readable instructions, or computer control logic) on acomputer-readable medium. The phrase “computer-readable medium”generally refers to any form of device, carrier, or medium capable ofstoring or carrying computer-readable instructions. Examples ofcomputer-readable media include, without limitation, transmission-typemedia, such as carrier waves, and physical media, such asmagnetic-storage media (e.g., hard disk drives and floppy disks),optical-storage media (e.g., CD- or DVD-ROMs), electronic-storage media(e.g., solid-state drives and flash media), and other distributionsystems.

The computer-readable medium containing the computer program may beloaded into computing system 510. All or a portion of the computerprogram stored on the computer-readable medium may then be stored insystem memory 516 and/or various portions of storage devices 532 and533. When executed by processor 514, a computer program loaded intocomputing system 510 may cause processor 514 to perform and/or be ameans for performing the functions of one or more of the exemplaryembodiments described and/or illustrated herein. Additionally oralternatively, one or more of the exemplary embodiments described and/orillustrated herein may be implemented in firmware and/or hardware. Forexample, computing system 510 may be configured as an applicationspecific integrated circuit (ASIC) adapted to implement one or more ofthe exemplary embodiments disclosed herein.

FIG. 6 is a block diagram of an exemplary network architecture 600 inwhich client systems 610, 620, and 630 and servers 640 and 645 may becoupled to a network 650. Client systems 610, 620, and 630 generallyrepresent any type or form of computing device or system, such asexemplary computing system 510 in FIG. 5.

Similarly, servers 640 and 645 generally represent computing devices orsystems, such as application servers or database servers, configured toprovide various database services and/or run certain softwareapplications. Network 650 generally represents any telecommunication orcomputer network including, for example, an intranet, a wide areanetwork (WAN), a local area network (LAN), a personal area network(PAN), or the Internet. In one example, client systems 610, 620, and/or630 and/or servers 640 and/or 645 may include system 100 from FIG. 1.

As illustrated in FIG. 6, one or more storage devices 660(1)-(N) may bedirectly attached to server 640. Similarly, one or more storage devices670(1)-(N) may be directly attached to server 645. Storage devices660(1)-(N) and storage devices 670(1)-(N) generally represent any typeor form of storage device or medium capable of storing data and/or othercomputer-readable instructions. In certain embodiments, storage devices660(1)-(N) and storage devices 670(1)-(N) may represent network-attachedstorage (NAS) devices configured to communicate with servers 640 and 645using various protocols, such as NFS, SMB, or CIFS.

Servers 640 and 645 may also be connected to a storage area network(SAN) fabric 680. SAN fabric 680 generally represents any type or formof computer network or architecture capable of facilitatingcommunication between a plurality of storage devices. SAN fabric 680 mayfacilitate communication between servers 640 and 645 and a plurality ofstorage devices 690(1)-(N) and/or an intelligent storage array 695. SANfabric 680 may also facilitate, via network 650 and servers 640 and 645,communication between client systems 610, 620, and 630 and storagedevices 690(1)-(N) and/or intelligent storage array 695 in such a mannerthat devices 690(1)-(N) and array 695 appear as locally attached devicesto client systems 610, 620, and 630. As with storage devices 660(1)-(N)and storage devices 670(1)-(N), storage devices 690(1)-(N) andintelligent storage array 695 generally represent any type or form ofstorage device or medium capable of storing data and/or othercomputer-readable instructions.

In certain embodiments, and with reference to exemplary computing system510 of FIG. 5, a communication interface, such as communicationinterface 522 in FIG. 5, may be used to provide connectivity betweeneach client system 610, 620, and 630 and network 650. Client systems610, 620, and 630 may be able to access information on server 640 or 645using, for example, a web browser or other client software. Suchsoftware may allow client systems 610, 620, and 630 to access datahosted by server 640, server 645, storage devices 660(1)-(N), storagedevices 670(1)-(N), storage devices 690(1)-(N), or intelligent storagearray 695. Although FIG. 6 depicts the use of a network (such as theInternet) for exchanging data, the embodiments described and/orillustrated herein are not limited to the Internet or any particularnetwork-based environment.

In at least one embodiment, all or a portion of one or more of theexemplary embodiments disclosed herein may be encoded as a computerprogram and loaded onto and executed by server 640, server 645, storagedevices 660(1)-(N), storage devices 670(1)-(N), storage devices690(1)-(N), intelligent storage array 695, or any combination thereof.All or a portion of one or more of the exemplary embodiments disclosedherein may also be encoded as a computer program, stored in server 640,run by server 645, and distributed to client systems 610, 620, and 630over network 650. Accordingly, network architecture 600 may performand/or be a means for performing, either alone or in combination withother elements, one or more of the identifying, obtaining, visuallyoverlaying, enabling, receiving, and providing steps disclosed herein.Network architecture 600 may also be used to perform and/or be a meansfor performing other steps and features set forth in the instantdisclosure.

As detailed above, computing system 510 and/or one or more components ofnetwork architecture 600 may perform and/or be a means for performing,either alone or in combination with other elements, one or more steps ofan exemplary method for displaying trustworthiness classifications forfiles as visually overlaid icons. For example, computing system 510 mayidentify a file and a file icon that graphically represents the filewithin a file manager interface on the computing device.

In some embodiments, computing system 510 may obtain a trustworthinessclassification assigned to the file that identifies the trustworthinessof the file. The trustworthiness classification may indicate that thefile is trustworthy, untrustworthy, or that the file's trustworthinessis unknown. Computing system 510 may then visually overlay the file iconwith a trustworthiness icon that graphically represents thetrustworthiness classification assigned to the file. For example,computing system 510 may provide a shell extension for the file managerinterface that causes the file manager interface to visually overlay thefile icon with the trustworthiness icon. This trustworthiness icon mayenable a user of the computing device to visually identify the file'strustworthiness without having to request a separate evaluation of thefile's trustworthiness.

In one or more embodiments, computing system 510 may obtain thetrustworthiness classification assigned from a reputation service. Insuch embodiments, this trustworthiness classification assigned to thefile may include information that identifies a reputation of the filewithin a community. The trustworthiness classification assigned to thefile may also be represented by a numeric score that identifies thefile's trustworthiness.

In at least one embodiment, computing system 510 may identify anadditional file and an additional file icon that graphically representsthe additional file within the same file manager interface as the fileicon. Computing system 510 may obtain an additional trustworthinessclassification assigned to the additional file that identifies thetrustworthiness of the additional file. Computing system 510 may thenvisually overlay the additional file icon with an additionaltrustworthiness icon that graphically represents the additionaltrustworthiness classification assigned to the additional file. Thisadditional trustworthiness icon may be juxtaposed with thetrustworthiness icon to enable the user to visually compare theadditional file's trustworthiness with the file's trustworthinesswithout having to request a separate evaluation of the additional file'strustworthiness.

While the foregoing disclosure sets forth various embodiments usingspecific block diagrams, flowcharts, and examples, each block diagramcomponent, flowchart step, operation, and/or component described and/orillustrated herein may be implemented, individually and/or collectively,using a wide range of hardware, software, or firmware (or anycombination thereof) configurations. In addition, any disclosure ofcomponents contained within other components should be consideredexemplary in nature since many other architectures can be implemented toachieve the same functionality.

In some examples, all or a portion of exemplary system 100 in FIG. 1 mayrepresent portions of a cloud-computing or network-based environment.Cloud-computing environments may provide various services andapplications via the Internet. These cloud-based services (e.g.,software as a service, platform as a service, infrastructure as aservice, etc.) may be accessible through a web browser or other remoteinterface. Various functions described herein may be provided through aremote desktop environment or any other cloud-based computingenvironment.

The process parameters and sequence of steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

While various embodiments have been described and/or illustrated hereinin the context of fully functional computing systems, one or more ofthese exemplary embodiments may be distributed as a program product in avariety of forms, regardless of the particular type of computer-readablemedia used to actually carry out the distribution. The embodimentsdisclosed herein may also be implemented using software modules thatperform certain tasks. These software modules may include script, batch,or other executable files that may be stored on a computer-readablestorage medium or in a computing system. In some embodiments, thesesoftware modules may configure a computing system to perform one or moreof the exemplary embodiments disclosed herein.

In addition, one or more of the modules described herein may transformdata, physical devices, and/or representations of physical devices fromone form to another. For example, one or more of modules 102 in FIG. 1may transform a characteristic or property of a physical device (such asdisplay device 524 in FIG. 5) by visually overlaying file icons withtrustworthiness icons.

The preceding description has been provided to enable others skilled inthe art to best utilize various aspects of the exemplary embodimentsdisclosed herein. This exemplary description is not intended to beexhaustive or to be limited to any precise form disclosed. Manymodifications and variations are possible without departing from thespirit and scope of the instant disclosure. The embodiments disclosedherein should be considered in all respects illustrative and notrestrictive. Reference should be made to the appended claims and theirequivalents in determining the scope of the instant disclosure.

Unless otherwise noted, the terms “a” or “an,” as used in thespecification and claims, are to be construed as meaning “at least oneof.” In addition, for ease of use, the words “including” and “having,”as used in the specification and claims, are interchangeable with andhave the same meaning as the word “comprising.”

1. A computer-implemented method for displaying trustworthinessclassifications for files as visually overlaid icons, at least a portionof the method being performed by at least one computing devicecomprising at least one processor, the method comprising: identifying afile; identifying a file icon that graphically represents the filewithin a file manager interface on the computing device; obtaining atrustworthiness classification assigned to the file that identifies thetrustworthiness of the file; visually overlaying the file icon with atrustworthiness icon that graphically represents the trustworthinessclassification assigned to the file, wherein the trustworthiness iconenables a user of the computing device to visually identify the file'strustworthiness without having to request a separate evaluation of thefile's trustworthiness.
 2. The computer-implemented method of claim 1,wherein the trustworthiness classification assigned to the fileindicates that at least one of: the file's trustworthiness is unknown;the file is untrustworthy; the file is trustworthy.
 3. Thecomputer-implemented method of claim 1, further comprising: identifyingan additional file; identifying an additional file icon that graphicallyrepresents the additional file within the same file manager interface asthe file icon; obtaining an additional trustworthiness classificationassigned to the additional file that identifies the trustworthiness ofthe additional file; visually overlaying the additional file icon withan additional trustworthiness icon that graphically represents theadditional trustworthiness classification assigned to the additionalfile, wherein the additional trustworthiness icon is juxtaposed with thetrustworthiness icon to enable the user to visually compare theadditional file's trustworthiness with the file's trustworthinesswithout having to request a separate evaluation of the additional file'strustworthiness.
 4. The computer-implemented method of claim 3, whereinthe file and the additional file comprise executable files that performsubstantially similar functions when executed by the computing device.5. The computer-implemented method of claim 3, wherein thetrustworthiness classification assigned to the file comprisesinformation that identifies a reputation of the file within a community.6. The computer-implemented method of claim 1, wherein obtaining thetrustworthiness classification assigned to the file comprises receivingthe trustworthiness classification from a reputation service.
 7. Thecomputer-implemented method of claim 1, wherein visually overlaying thefile icon with the trustworthiness icon comprises providing a shellextension for the file manager interface that causes the file managerinterface to visually overlay the file icon with the trustworthinessicon.
 8. The computer-implemented method of claim 1, wherein thetrustworthiness classification assigned to the file is represented by anumeric score that identifies the file's trustworthiness.
 9. A systemfor displaying trustworthiness classifications for files as visuallyoverlaid icons, the system comprising: an identification moduleprogrammed to: identify a file; identify a file icon that graphicallyrepresents the file within a file manager interface on the computingdevice; a classification module programmed to obtain a trustworthinessclassification assigned to the file that identifies the trustworthinessof the file; an overlay module programmed to visually overlay the fileicon with a trustworthiness icon that graphically represents thetrustworthiness classification assigned to the file, wherein thetrustworthiness icon enables a user of the computing device to visuallyidentify the file's trustworthiness without having to request a separateevaluation of the file's trustworthiness; at least one processorconfigured to execute the identification module, the classificationmodule, and the overlay module.
 10. The system of claim 9, wherein thetrustworthiness classification assigned to the file indicates that atleast one of: the file's trustworthiness is unknown; the file isuntrustworthy; the file is trustworthy.
 11. The system of claim 9,wherein: the identification module is further programmed to: identify anadditional file; identify an additional file icon that graphicallyrepresents the additional file within the same file manager interface asthe file icon; the classification module is further programmed to obtainan additional trustworthiness classification assigned to the additionalfile that identifies the trustworthiness of the additional file; theoverlay module is further programmed to visually overlay the additionalfile icon with an additional trustworthiness icon that graphicallyrepresents the additional trustworthiness classification assigned to theadditional file, wherein the additional trustworthiness icon isjuxtaposed with the trustworthiness icon to enable the user to visuallycompare the additional file's trustworthiness with the file'strustworthiness without having to request a separate evaluation of theadditional file's trustworthiness.
 12. The system of claim 11, whereinthe file and the additional file comprise executable files that performsubstantially similar functions when executed by the computing device.13. The system of claim 11, wherein the trustworthiness classificationassigned to the file comprises information that identifies a reputationof the file within a community.
 14. The system of claim 9, wherein theclassification module is further programmed to receive thetrustworthiness classification from a reputation service.
 15. The systemof claim 9, wherein the overlay module is further programmed to providea shell extension for the file manager interface that causes the filemanager interface to visually overlay the file icon with thetrustworthiness icon.
 16. The system of claim 9, wherein thetrustworthiness classification assigned to the file is represented by anumeric score that identifies the file's trustworthiness.
 17. Anon-transitory computer-readable-storage medium comprising one or morecomputer-executable instructions that, when executed by at least oneprocessor of a computing device, cause the computing device to: identifya file; identify a file icon that graphically represents the file withina file manager interface on the computing device; obtain atrustworthiness classification assigned to the file that identifies thetrustworthiness of the file; visually overlay the file icon with atrustworthiness icon that graphically represents the trustworthinessclassification assigned to the file, wherein the trustworthiness iconenables a user of the computing device to visually identify the file'strustworthiness without having to request a separate evaluation of thefile's trustworthiness.
 18. The non-transitory computer-readable-storagemedium of claim 17, wherein the trustworthiness classification assignedto the file indicates that at least one of: the file's trustworthinessis unknown; the file is untrustworthy; the file is trustworthy.
 19. Thenon-transitory computer-readable-storage medium of claim 17, wherein theone or more computer-executable instructions, when executed by thecomputing device, further cause the computing device to: identify anadditional file; identify an additional file icon that graphicallyrepresents the additional file within the same file manager interface asthe file icon; obtain an additional trustworthiness classificationassigned to the additional file that identifies the trustworthiness ofthe additional file; visually overlay the additional file icon with anadditional trustworthiness icon that graphically represents theadditional trustworthiness classification assigned to the additionalfile, wherein the additional trustworthiness icon is juxtaposed with thetrustworthiness icon to enable the user to visually compare theadditional file's trustworthiness with the file's trustworthinesswithout having to request a separate evaluation of the additional file'strustworthiness.
 20. The non-transitory computer-readable-storage mediumof claim 19, wherein the file and the additional file compriseexecutable files that perform substantially similar functions whenexecuted by the computing device.